ci: fix amicode-release UI gate check for the unconditional layout memo - #81

Release blocker

ead3274d3 ("lock down appearance settings; force v2 layout", 2026-07-24 — after v1.17.3-amicode.9) changed settings.tsx to:

newLayoutDesigns: createMemo(() => true)

That minifies to newLayoutDesigns:Z(()=>!0). The gate check greps for the old channel-gated shape newLayoutDesigns,<VAR>), finds nothing, and exits 1.

Any release cut from current mainline fails the Gate check step and never publishes. Found while building the branch for #73 locally:

$ VAR=$(grep -aoh 'newLayoutDesigns,[A-Za-z$_]\{1,8\})' "$BIN" | ...)
VAR=
FAIL: pattern not found

The change itself is good — the setting no longer depends on the build channel at all, so the original failure mode (channel latest/prod defaults it OFF) is structurally gone. Only the check needs to catch up.

Fix

Accept the new unconditional shape, keep the legacy channel-gated shape as a fallback in case the setting is ever rewired to the channel default, and still fail loudly on genuine drift.

Also fixes two latent set -e bugs that made this check exit silently rather than report:

1. grep -aq '…' && { echo FAIL; exit 1; } — under set -e a non-matching grep in an AND-list aborts the whole step with no message.
2. VAR=$(grep … | head … | sed …) — under set -o pipefail a no-match grep aborts the assignment. This is pre-existing: it means the existing "FAIL: gate pattern not found" diagnostic could never actually print. The step just died with no explanation, which is exactly what happened above.

Verification

Extracted check() from the workflow and ran it against four binaries:

Case 2 confirms the legacy path still works; cases 3 and 4 confirm it fails for the right reasons with a usable message.

Note

This is independent of #73 (the provider/model port) — it blocks releases either way and should land first.